BBS Toolkit/BBS Toolkit.iso/pc_board/zl2b0307.zip/BETA.HST

Text File | 1993-03-07 | 13KB | 262 lines

ZipLab Plus 2.ß (BETA)
Beta version history file


IF THIS IS THE FIRST VERSION OF ZIPLAB 2.0 BETA WHICH YOU ARE TRYING, DON'T
EVEN BOTHER WITH THIS FILE.  JUST READ AND FOLLOW THE DIRECTIONS IN THE
FILE "ZIPLAB.DOC".

IF YOU ARE UPGRADING FROM A BETA OTHER THAN THE ONE IMMEDIATLY PRECEEDING
THIS ONE, DON'T WORRY ABOUT GETTING CAUGHT UP.  THE DIRECTIONS FOR SETTING
UP THIS VERSION (BOTH HERE AND IN ZIPLAB.DOC) WILL GET YOU CURRENT.

2.ß.13 - March 7, 1993
**********************

NO CHANGES ARE REQUIRED FROM 02/20.  Just unzip the ZLAB.EXE file over the
old one, and you are all set.

1) I have fixed the cosmetic and functional bugs with the dates being switched
   (New and Old).

2) I have fixed the problem you sometimes had on a failed file in LOCAL mode,
   with a FUBAR=3600 (Problem adding reason to description file).

3) I think I have stomped out the other LOCAL mode problem that sometimes gave
   a FUBAR=820 (CALLER file not found)


OUTSTANDING CURRENT ITEMS:  These items will be in 2.0 at some point.

* Don't check "bbs ads" on date limit validation (it does now...)
* A version of ZCRC.EXE which accepts DOS "wildcards"
* Allow one "user defined" function in ZipLab.

OUTSTANDING FUTURE ITEMS:  These requests may or may not make version 2.0

* "between callers" testing.  Test the file after the user has
  hung up. - Likely...
* Have files failed for AGE or TCAN put
  in the UPSEC. file so they won't be
  uploaded again. - Maybe...
* Add -AV information to the description

OTHER OUTSTANDING ITEMS:
* Generic version - next major effort
* WildCat! version - after generic



2.ß.12 - February 20, 1993
**************************

A hard drive crash here caused a mixup with the code in the 02/17 version,
and a few bugs crept in.  Please just unzip the ZLAB.EXE and ZVALID.EXE
programs over your 02/17 version, and you are all set.



2.ß.11 - February 17, 1993
**************************

A CHANGE TO YOUR ZLABxxx.CFG FILE(S) IS REQUIRED!  PLEASE READ CAREFULLY!

Not too many changes this go-round, but the changes made are significant.

1)  The keyword "DateLimit=" in your ZLABxxx.CFG file(s) has been replaced.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    The new keyword is "AgeDays=", and should be set to a NUMBER OF DAYS
    old you wish to allow for acceptable uploads.  Now you should never
    have to change this field again, once set.  It will subtract the
    number in "AgeDays" from the system date, and anything older than that
    will fail.  Please remove the line containing "DateLimit=yyyymm", and
    replace with "AgeDays=xxx" (where "xxx" is the number of days).
    Example:  AgeDays=730

2)  ZipLab now supports the "/M" version of PCBoard.  Fossil support is
    transparent as far as your configuration goes.  ZipLab will detect
    that you are running in Fossil mode, and use the appropriate comm
    routines.  Boocoup thanks to Phil Gordemer of Compu-Data BBS for
    his help with testing the Fossil routines.

3)  In my never-ending struggle to get all the GIFTEST problems fixed,
    I have included the and older (beta 10) version of the executable
    GIFTEST.EXE.  I have run this version to death on my system, and
    can not get it to break in any way.  I do NOT use the .CFG file
    option, but specify /M:640x480x16 (the resolution), the /B:x (1 for
    PCB, 2 for ProDoor), and the /F:drive:\path\filename (the location
    of the "description file" - updesc.x for PCBoard, c:\pcb\$door.nam
    for ProDoor).  I have used "for %a in (*.gif) do zlab... %a" on a
    whole directory of .GIF files, with a mixture of good and bad ones,
    and it seems to work fine.  Newer versions of Giftest (like the
    beta 16f going around now) just don't seem to work right.  I don't
    know what else to say or do...  My apologies to Max, but there is
    just something wrong with the newer versions.  Please let me know
    if this version works for you.  If so, I am going to have to
    recommend that we just stay with this one until something is done
    by Max.  If not, I am going to ask you to run Giftest outside
    of ZipLab.  I will not spend any more time on a program that I
    have no control over.

4)  If you were having ZipLab directly modify an archive file by deleting
    a "bbs ad", or adding a file to the archive, the date of the archive
    was being reset to the current date.  ZipLab will now maintain the
    original date and time.

5)  The output of ZDCS when you return to PCBoard/ProDoor is now being
    supressed, unless the file FAILS ZDCS checking.  You won't have to
    look at a whole screen full of file names, when they all pass dupe
    checking.

6)  Lots of work on the communications routines, to try and stamp out
    a problem when running inside PCBoard on a local (no comm port)
    node.  There was times that this would cause "bleed-through" on
    DV nodes, and/or mess with the comm port on other nodes connected
    to the same machine.  This should all be corrected.

7)  I had let support for DESC.SDI kinda die, as FILE_ID.DIZ is the
    clear winner in the "description file" arena.  I have added full
    support for DESC.SDI back in, to please some purists <grin>.

8)  In some cases, a non "archive" file was passing even if older than
    the allowable date.  Fixed.

9)  The sample .MSG (message files) and .CMT (comment file) which I
    included in the 01/31 beta where still using the old @ZCode
    format.  Fixed.




2.ß.10 - January 31, 1993
*************************

MAJOR CHANGES FROM ANY PREVIOUS BETA!  PLEASE READ CAREFULLY BEFORE
OVERLAYING ANY EXISTING ZIPLAB SETUP.

ZipLab Plus has undergone major changes to improve ease of installation,
performance, and features.

First, let's talk about what has changed in a general sense, before getting
to the quick upgrade section.

1)  ZipLab Plus is now fully integrated with the ZDCS duplicate checking
    system from Mike Cocke.  If you have ZDCS version 2.01 or better, ZipLab
    will call ZDCS to do your duplicate checking, with ZDCS allowing ZipLab
    to handle all screen output to the user.  ZDCS is (C)1993 by M.W.Cocke,
    and does require regisration with Mike for use beyond a 30 day trial
    period. If you are a registered ZDCS owner, ZipLab will detect this, and
    will inform your users of your support for Shareware.  If not, ZipLab
    will display an "UNREGISTERED ZDCS" notice during ZDCS processing.
    Thanks to Mike Cocke for allowing this integration with ZDCS, and for his
    work in modifying his program to facilitate it's use with ZipLab Plus.

2)  The ZLABxxx.CFG files have been COMPLETELY re-designed!  They now follow
    a format similar to Windows ".INI" files, with each line having ZipLab
    "keywords" followed by your values.  Please modify and use the fully
    commented sample ZLAB000.CFG I have included with the archive. Editing
    your .CFG file is now a lot simpler, and ZipLab Plus has the built-in
    ability to detect most configuration problems and suggest solutions.

3)  As well as the built-in checking of the .CFG files at runtime, there is
    also a new ZVALID.EXE program which will allow you to test the contents
    of your ZLABxxx.CFG files for validity right after editing.  A report
    "ZVALID.RPT" will be produced, informing you of any configuration errors.

4)  The ZSET.EXE configuration editor has been eliminated.  The new format
    of the ZLABxxx.CFG files makes it a breeze to configure with a simple
    text editor.  The sample ZLAB000.CFG provided in this archive is fully
    commented with explanations for each keyword.  These explanations can
    be left in the file as reference for future editing.  Please do not
    edit any new ZLABxxx.CFG files with ZSET.EXE, just erase it.

5)  The format of the @ZCodes have been changed.  At the request of several
    sysops, the "memonics" have been expanded to make them easier to
    remember.  The file ZCODES.NEW explains the required changes, and the
    included FIXCODES.EXE program will make the changes in your .MSG and .CMT
    files for you.

6)  ZipLab now has an option allowing you to specify that you want all those
    "fail" mail messages sent to either your Main Board, or to the current
    conference.

7)  The routines which check CRC.ADS and LST.ADS for BBS advertising have
    been completely reworked.  You may now have up to 5000 lines in each
    of these files, and the processing time has been reduced over 90%!
    The format of the CRC.ADS and LST.ADS files has NOT changed.  Your
    existing files require no modification.

8)  Ziplab's error trapping and handling system has been completely redone.
    The included file ZERROR.DAT needs to be in the directory with your
    .CFG file(s).  Much more accurate error reporting is now provided,
    with codes that you can relay to me if you are unable to resolve a
    problem.  These codes should allow me to zero in on the problem in
    almost all cases.

9)  There is a new ZSHELL.EXE file which is called by ZipLab to reduce
    memory problems during "shells" to external programs like PKUNZIP.
    This program has an entry in ZLABxxx.CFG, to allow Ziplab to find it.
    ZSHELL.EXE should not be run alone, but will be called by ZipLab.

10) Lots of cosmetic and performance changes that you don't have to
    worry about, just enjoy...


Quick Upgrade from any previous verion -

1)  Get a copy of ZDCS 2.01 or better from the Hacker's Central BBS. As of
    right now, that is the ONLY place you can get it.  The phone number
    there is (201)-335-9343.  You can run the 2.0 version, available lots of
    places, but the cosmetic integration will be imperfect.  Mike has said
    that he will allow first-time callers to download the 2.01 version of
    ZDCS for testing with ZipLab.  This is optional, and ZipLab will operate
    just fine without ZDCS, but I do recommend the program.

2)  Set up ZDCS and create its database.  Please follow the directions
    in the the documentation for ZDCS - I like the program, but DON'T
    provide technical support for it!  One note, do NOT have ZDCS erase
    or move any failed files.. Let ZipLab take care of it.

3)  Erase ZSET.EXE - don't need it any more.

4)  PRINT your ZLABxxx.CFG file(s), and then erase them.. They are
    going to be completly reworked anyway.

5)  Overlay your current ZLAB.EXE file with the new one in this archive.

6)  Copy ZSHELL.EXE to your ZIPLAB directory.

7)  Copy ZERROR.DAT and ZVALID.EXE to the directory containing your .CFG
    files.

8)  Copy FIXCODES.EXE to the directory containing your .MSG and .CMT
    files (not required if you don't use @ZCODES in them).  Run
    "FIXCODES filename" for each of your .MSG files and .CMT files
    that contain @ZCODES.

9)  Using a text editor, edit my sample ZLAB000.CFG file, replacing
    my values which follow the ZipLab "keywords" with values that
    relect your system.  The bottom half of ZLAB000.CFG has descriptions
    of all the keywords, and you should find it all very simple and
    self-explanatory.  If not, time to print ZIPLAB.DOC, which has
    greater detail on setting up the .CFG file.  The .CFG files are
    NOT case sensitive in any way.

10) After saving the modified ZLAB000.CFG, run "ZVALID ZLAB000.CFG".
    A report "ZVALID.RPT" will be created in the current directory.
    take a look at this report, and note any places where it finds
    errors or missing items.  Re-edit the file and re-run ZVALID
    until it comes up with a straight column of "OK!" on the right.
    Your configuration file will now be correct.

11) Make copies of ZLAB000.CFG, replacing the "000" with any
    conference specific config files you wish.  Then edit those
    to change any values specific to those conferences.

11) Test with the "LOCAL" keyword from DOS, use the "TEST" command
    from a local login to your board, and perform a local "UPLOAD"
    while in the board.  Assuming that all goes well, you are DONE!